Avoid MCOMPILER-485 in compiler plugin 3.10.0#506
Conversation
Maven 3.10.0 added a feature to create missing package-info files. The feature incorrectly uses Windows-style directory separators on Windows. Other parts of the code expect to always see Unix style directory separators. Disable the new feature so that it does not break compilation. https://groups.google.com/g/jenkinsci-dev/c/077VYgtSLXo/m/6JQjJs7-AQAJ
|
Amending #504. |
jglick
left a comment
jglick
left a comment
There was a problem hiding this comment.
Does this fix the problem in git-plugin?
|
I see the fix is merged, @olamy will it be released soon? ❤️ |
does this break Jenkins build or not? (sorry I do not have windauze to test that) As Jenkins is not yet build with Java 11 (neither using really soon jpms features) there is probably nothing urgent here ;) |
|
LOL I did not even read the content of the PR but only the comment 🤣 |
|
@olamy any idea when apache/maven-compiler-plugin#95 will be released? |
|
Released this as 4.36, along with a mojo fix from @basil. |
4 participants
Avoid MCOMPILER-485 in compiler plugin 3.10.0
Maven 3.10.0 added a feature to create missing package-info files. The feature incorrectly uses Windows-style directory separators on Windows. Other parts of the code expect to always see Unix style directory separators.
Disable the new feature so that it does not break compilation. See Jenkins developer mailing list conversation for details.
I'm not expert enough in Maven development to create the integration test to confirm the issue is resolved. I assume it would require a Java package that does not have a package-info file and then a check on Windows that some internal path to the generated package-info file is using Windows directory separators.